Serving WebObjects
 (September 1999)(Disk 2).iso/Technical Publications/webobjects/images/wothinban.gif)
PATH
WebObjects 4.0 Documentation >
Serving WebObjects
 (September 1999)(Disk 2).iso/Technical Publications/webobjects/System/Documentation/Developer/WebObjects/ServingWebObjects/ArrowUp.gif)
Table of Contents  (September 1999)(Disk 2).iso/Technical Publications/webobjects/System/Documentation/Developer/WebObjects/ServingWebObjects/ArrowLeft.gif)
Previous Section
Deploying on Multiple Hosts
Creating a deployment environment sometimes involves more than one HTTP server and many WebObjects application instances running on each server. The Monitor application is designed to run on a single machine. Thus there can only be one copy of Monitor running at a time and managing the same set of hosts. To make several hosts available to Monitor, a service called MonitorProxy must be running. With a MonitorProxy running the Monitor application can remotely administer a host machine.
A large WebObjects deployment could be depicted as in the following diagram:
 (September 1999)(Disk 2).iso/Technical Publications/webobjects/System/Documentation/Developer/WebObjects/ServingWebObjects/DeployingMultipleHosts.gif)
Machine 1 acts as the web server and load balancer between all the application servers running on Machines 2, 3, and 4. You should run Monitor on the same host as the web server and the WebObjects adaptor since Monitor is involved in modifying and updating the WebObjects.conf file. which the adaptor uses to find instances.
Table of Contents  (September 1999)(Disk 2).iso/Technical Publications/webobjects/System/Documentation/Developer/WebObjects/ServingWebObjects/ArrowRight.gif)
Next Section